docs: standardize docstrings for ARModel init - #488
Closed
PalaniappanR02 wants to merge 3 commits into
Closed
Conversation
Collaborator
|
@PalaniappanR02 no separate PR needed here, you can add these suggestions for docstrings directly in #252 . also the pr template is missing. The remaining part of the work regarding docstrings is probably going through all of them in #252 and make sure they are correct and uniform |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi @sadamov! As discussed on GitHub, I'm starting to standardize docstrings to match the NumPy style established in #252 to support the autodoc implementation in #196.
This PR updates the init method for the ARModel class. I plan to continue this across the models module. Feedback is welcome!